Release 0.8.0 - #97
Merged
Merged
Conversation
All eight version strings and the four lockfiles that carry them. The release guard checks only `apps/cli/Cargo.toml` and `tauri.conf.json` (issue #77), so the other six are bumped by hand and by eye until that is fixed. Minor rather than patch: two features landed since v0.7.0 (post-compression verification, and asking the user which characters to substitute in a name the host cannot write), alongside a fix for writing outside the output directory.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump only. No behaviour changes.
All eight version strings plus the four lockfiles that carry them. The release guard validates only
apps/cli/Cargo.tomlandapps/desktop/src-tauri/tauri.conf.json, so the remaining six are bumped by hand and would drift unnoticed (#77).cargo build --lockedwas run afterwards, since that is whatmake cli/releaseuses and a drifted lockfile fails there first.What is in this release
Six PRs since v0.7.0.
Features
Fixes
#[cfg]-dependent while the rules judging them are data. On Unix that made a legal file name unextractable, so collapse could build an archive it then refused to open. On Windows a leading drive-like component was silently discarded, which was a hole in the colon handling of core: an entry name with a colon passes the traversal guard and becomes an NTFS stream on Windows聽#63 on the only platform core: an entry name with a colon passes the traversal guard and becomes an NTFS stream on Windows聽#63 concerns. Same PR closes a path traversal: zip and 7z wrote through a symlink already present in the output directory, which tar had always refused. That one predates v0.7.0.Photos.ZIPopens.Verification
585 Rust tests and 113 Vitest, now on three platforms rather than one.
test (rust, windows)andtest (rust, macos)run on shipping branches, which is what caught #88, and this being arelease/*branch is what makes them run here too.Issues
#63 and #64 are complete and close with this release. The keywords are deliberately not here: the default branch is
main, so GitHub ignores them on a PR intodev. They go on the dev-into-main PR.Nothing else on the board is finished, so this release closes two issues and no more.